Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae6f8f4032c35dabb0b4d450e33c4d23703e384affecc5b4fbf62ad3da1de951

Tx prefix hash: aa39491901bd715c31e1baf8a724f0bf283ae393a03d7562a8bdda8a98074c47
Tx public key: 655b9ffa1a3789faf1f02ccd035529cb33b19c8373d59b3514b4e0248f6f4708
Timestamp: 1697237175 Timestamp [UCT]: 2023-10-13 22:46:15 Age [y:d:h:m:s]: 01:192:12:40:59
Block: 869043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398635 RingCT/type: yes/0
Extra: 01655b9ffa1a3789faf1f02ccd035529cb33b19c8373d59b3514b4e0248f6f470802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.810027593000 dcy

stealth address amount amount idx
00: bec3974b25dff5d55b01fc15e5abd8e521f003a85a6275b53642aee1cc7df5f7 0.810027593000 1323870 of 0

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": 869053, "vin": [ { "gen": { "height": 869043 } } ], "vout": [ { "amount": 810027593, "target": { "key": "bec3974b25dff5d55b01fc15e5abd8e521f003a85a6275b53642aee1cc7df5f7" } } ], "extra": [ 1, 101, 91, 159, 250, 26, 55, 137, 250, 241, 240, 44, 205, 3, 85, 41, 203, 51, 177, 156, 131, 115, 213, 155, 53, 20, 180, 224, 36, 143, 111, 71, 8, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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