Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d66321788e3919d38c797dbbce630a2c78e1ef5bbd4baf846c54bf70f09aaf

Tx prefix hash: bc705996864f206e262b157a66e3de1a81db6b7194abf7fa26f60233e093f5f3
Tx public key: f78188df7b525a3cd9f9a961f25b6d7f3ab26028b0028a999b3b36b03f9df694
Timestamp: 1728375176 Timestamp [UCT]: 2024-10-08 08:12:56 Age [y:d:h:m:s]: 01:036:23:05:47
Block: 1126991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284807 RingCT/type: yes/0
Extra: 01f78188df7b525a3cd9f9a961f25b6d7f3ab26028b0028a999b3b36b03f9df694021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9346af7a665fc4c514f2c61d31e7588a7db0d1b1ceba0270616b7aa4cc8836c7 0.600000000000 1609790 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": 1127001, "vin": [ { "gen": { "height": 1126991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9346af7a665fc4c514f2c61d31e7588a7db0d1b1ceba0270616b7aa4cc8836c7" } } ], "extra": [ 1, 247, 129, 136, 223, 123, 82, 90, 60, 217, 249, 169, 97, 242, 91, 109, 127, 58, 178, 96, 40, 176, 2, 138, 153, 155, 59, 54, 176, 63, 157, 246, 148, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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