Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a83c3ac3a932245bec7ce9ae984d8ac8e19dbe80244aaa86752ac23fd31b1ea2

Tx prefix hash: 60fc532912459f88133a0cb56d9d421c0275df6184a899fcbdff4b29b791fc5f
Tx public key: 5afd62052a65b2df2e70b90d697ca5b5272e008ecf8deefb7a3736df65123dd7
Timestamp: 1709578206 Timestamp [UCT]: 2024-03-04 18:50:06 Age [y:d:h:m:s]: 00:325:12:46:07
Block: 971156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232981 RingCT/type: yes/0
Extra: 015afd62052a65b2df2e70b90d697ca5b5272e008ecf8deefb7a3736df65123dd702110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60ea216012e12d63abbe82ca6cdc4ac6d30ae75e0a9b0ff91f5bc2948573950a 0.600000000000 1431041 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": 971166, "vin": [ { "gen": { "height": 971156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60ea216012e12d63abbe82ca6cdc4ac6d30ae75e0a9b0ff91f5bc2948573950a" } } ], "extra": [ 1, 90, 253, 98, 5, 42, 101, 178, 223, 46, 112, 185, 13, 105, 124, 165, 181, 39, 46, 0, 142, 207, 141, 238, 251, 122, 55, 54, 223, 101, 18, 61, 215, 2, 17, 0, 0, 0, 8, 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