Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e00be8fac6b0e157a9a6bc6e6a5cd37f0c2525c155447033d282ed3718f46997

Tx prefix hash: b729f81f39d7dd1cab878fea14576b8d9a632dff37c124a7e3c5775a3298e8a2
Tx public key: d012f2d800dc26cede5c45fabb9270a3e491a1987f45fc6d848dd83fea0aed0f
Timestamp: 1733574312 Timestamp [UCT]: 2024-12-07 12:25:12 Age [y:d:h:m:s]: 00:113:13:50:59
Block: 1169986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80969 RingCT/type: yes/0
Extra: 01d012f2d800dc26cede5c45fabb9270a3e491a1987f45fc6d848dd83fea0aed0f021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 665dc32918cd38c4cd63956eddf449ab20b38b21df74cf0b39b1ddb933bb5eb4 0.600000000000 1655713 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": 1169996, "vin": [ { "gen": { "height": 1169986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "665dc32918cd38c4cd63956eddf449ab20b38b21df74cf0b39b1ddb933bb5eb4" } } ], "extra": [ 1, 208, 18, 242, 216, 0, 220, 38, 206, 222, 92, 69, 250, 187, 146, 112, 163, 228, 145, 161, 152, 127, 69, 252, 109, 132, 141, 216, 63, 234, 10, 237, 15, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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