Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bbabbf6a54f9c4e83393b4470daec5638765b07d48252bab03dcf215b3f7a07

Tx prefix hash: 6ffcaa6697fcb361b18ba9702dbba8c5f9828a52f6cb53ed0e1b453a6fb85dd0
Tx public key: b6a302f900b9fd751eb37dff0b3b279f90d401801f81340a11faf6bf50aa6397
Timestamp: 1722131384 Timestamp [UCT]: 2024-07-28 01:49:44 Age [y:d:h:m:s]: 00:239:07:42:44
Block: 1075222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170941 RingCT/type: yes/0
Extra: 01b6a302f900b9fd751eb37dff0b3b279f90d401801f81340a11faf6bf50aa639702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa648dae8adaedfe15270a32f34f7161475f9477ae6fe43d0e8f72ece1acde81 0.600000000000 1547745 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": 1075232, "vin": [ { "gen": { "height": 1075222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa648dae8adaedfe15270a32f34f7161475f9477ae6fe43d0e8f72ece1acde81" } } ], "extra": [ 1, 182, 163, 2, 249, 0, 185, 253, 117, 30, 179, 125, 255, 11, 59, 39, 159, 144, 212, 1, 128, 31, 129, 52, 10, 17, 250, 246, 191, 80, 170, 99, 151, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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