Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 031ef513692a807718b2b6c62333d9e9d5501d38149f6873e21dfc8815eb02aa

Tx prefix hash: 07f5547e2a162c430d89033c0388dd21a1c995e614c4d34b09244a86c84f84fe
Tx public key: d70d0cedc8e774d08e9814cde713c77edeaf4a4c71a04926b7f8379335d71bbc
Timestamp: 1726335909 Timestamp [UCT]: 2024-09-14 17:45:09 Age [y:d:h:m:s]: 00:161:16:52:29
Block: 1110083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115361 RingCT/type: yes/0
Extra: 01d70d0cedc8e774d08e9814cde713c77edeaf4a4c71a04926b7f8379335d71bbc021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d4424a3f54046747737f6c7afcfda30de1dd7b8bbac8814b913879fe609c0d5 0.600000000000 1588564 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": 1110093, "vin": [ { "gen": { "height": 1110083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d4424a3f54046747737f6c7afcfda30de1dd7b8bbac8814b913879fe609c0d5" } } ], "extra": [ 1, 215, 13, 12, 237, 200, 231, 116, 208, 142, 152, 20, 205, 231, 19, 199, 126, 222, 175, 74, 76, 113, 160, 73, 38, 183, 248, 55, 147, 53, 215, 27, 188, 2, 17, 0, 0, 0, 2, 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