Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 89c56d1912246e5bf3d0e59283641097d69691cd012975cb922259d92dfc562c

Tx prefix hash: 478c7e671ebd839e61068ac67f4a01be7581e00b617d20f74a4d3e1cd34fa52c
Tx public key: a9f9733bb36ffa3281b9b5cc6e9dd927caba317fb6332894a0d9a95d2b729fa8
Timestamp: 1715178766 Timestamp [UCT]: 2024-05-08 14:32:46 Age [y:d:h:m:s]: 00:358:20:52:58
Block: 1017602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256520 RingCT/type: yes/0
Extra: 01a9f9733bb36ffa3281b9b5cc6e9dd927caba317fb6332894a0d9a95d2b729fa802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfc6923cdb79ced993c47dad5f0ce027841f7040c01bea2795fae0d6080c9100 0.600000000000 1481385 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1017612, "vin": [ { "gen": { "height": 1017602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfc6923cdb79ced993c47dad5f0ce027841f7040c01bea2795fae0d6080c9100" } } ], "extra": [ 1, 169, 249, 115, 59, 179, 111, 250, 50, 129, 185, 181, 204, 110, 157, 217, 39, 202, 186, 49, 127, 182, 51, 40, 148, 160, 217, 169, 93, 43, 114, 159, 168, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8