Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a552968ff9b603f0f1562dc8a7b9282641ee919f1cdb3b2cdd48071392a39f

Tx prefix hash: 47e5080f93e41d5958c4dece7229aae9e3737e75316680b8b863f07d819b8b9d
Tx public key: cf490ae3807cda52277449dbfe2ff2aeef6b42a196f0bac0b01c039d122339f4
Timestamp: 1733139026 Timestamp [UCT]: 2024-12-02 11:30:26 Age [y:d:h:m:s]: 00:144:18:57:35
Block: 1166379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103299 RingCT/type: yes/0
Extra: 01cf490ae3807cda52277449dbfe2ff2aeef6b42a196f0bac0b01c039d122339f4021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c51aef592da376ec0fd88e06ea15bef1a8475a61bec53531de1d0370c122554 0.600000000000 1652066 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": 1166389, "vin": [ { "gen": { "height": 1166379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c51aef592da376ec0fd88e06ea15bef1a8475a61bec53531de1d0370c122554" } } ], "extra": [ 1, 207, 73, 10, 227, 128, 124, 218, 82, 39, 116, 73, 219, 254, 47, 242, 174, 239, 107, 66, 161, 150, 240, 186, 192, 176, 28, 3, 157, 18, 35, 57, 244, 2, 17, 0, 0, 0, 1, 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