Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd80171282172989fc442c78203b32a196e19aeee7a41f819a91322f06f5ce9b

Tx prefix hash: 19401d94fbe9e0cd8e7474531355d097e89a252c4beb40f288a0bc805e3a7e11
Tx public key: 508ed49ec4d23c74d832acb4b806094f4db3cf058bf3bdc2b475bfb9df975367
Timestamp: 1719282825 Timestamp [UCT]: 2024-06-25 02:33:45 Age [y:d:h:m:s]: 00:291:00:13:21
Block: 1051601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207959 RingCT/type: yes/0
Extra: 01508ed49ec4d23c74d832acb4b806094f4db3cf058bf3bdc2b475bfb9df9753670211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 130acc38e4287a5983c36f89dcc341fb94f0ccc86b7303dc9a3315dd1fc573e0 0.600000000000 1521916 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": 1051611, "vin": [ { "gen": { "height": 1051601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "130acc38e4287a5983c36f89dcc341fb94f0ccc86b7303dc9a3315dd1fc573e0" } } ], "extra": [ 1, 80, 142, 212, 158, 196, 210, 60, 116, 216, 50, 172, 180, 184, 6, 9, 79, 77, 179, 207, 5, 139, 243, 189, 194, 180, 117, 191, 185, 223, 151, 83, 103, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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