Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eae69e6445a8cf1bac8f55da2ee5aa096aaa01b406d9d7e9060053d3581f004

Tx prefix hash: 6493fae5fa29115edbe4f172f899ccbd059588539f8e9a2e5a87241302d7a73a
Tx public key: 33d20f717fe585dec92dabe8b1a2efff484ea3394df08408e9f46ab9cbcf3d5e
Timestamp: 1705004832 Timestamp [UCT]: 2024-01-11 20:27:12 Age [y:d:h:m:s]: 01:136:22:05:08
Block: 933221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359002 RingCT/type: yes/0
Extra: 0133d20f717fe585dec92dabe8b1a2efff484ea3394df08408e9f46ab9cbcf3d5e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cdd34eb3da5d04dba4f299d5896af4339a2b51820c26453220290154515752e 0.600000000000 1391181 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": 933231, "vin": [ { "gen": { "height": 933221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cdd34eb3da5d04dba4f299d5896af4339a2b51820c26453220290154515752e" } } ], "extra": [ 1, 51, 210, 15, 113, 127, 229, 133, 222, 201, 45, 171, 232, 177, 162, 239, 255, 72, 78, 163, 57, 77, 240, 132, 8, 233, 244, 106, 185, 203, 207, 61, 94, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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