Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84a44e2a0eb208edccb24354e91d19926c50a0d392fe65d73faed2b3fa18774

Tx prefix hash: 0e03eaf5c4877caaa0ca8a6d234c2670db804806815978f9a59c291c43d0ff4c
Tx public key: 8bc992faa639147785011bf7e83ad77f0b8d5874433dc9a5e0e6899998ea1e77
Timestamp: 1681119743 Timestamp [UCT]: 2023-04-10 09:42:23 Age [y:d:h:m:s]: 02:000:15:19:45
Block: 735461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522612 RingCT/type: yes/0
Extra: 018bc992faa639147785011bf7e83ad77f0b8d5874433dc9a5e0e6899998ea1e7702110000000274b6d784000000000000000000

1 output(s) for total of 2.244463913000 dcy

stealth address amount amount idx
00: a514cba3f0f340a265aee2ded774c2089c77769d7d4c821ae3576c1e96e8c102 2.244463913000 1181790 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": 735471, "vin": [ { "gen": { "height": 735461 } } ], "vout": [ { "amount": 2244463913, "target": { "key": "a514cba3f0f340a265aee2ded774c2089c77769d7d4c821ae3576c1e96e8c102" } } ], "extra": [ 1, 139, 201, 146, 250, 166, 57, 20, 119, 133, 1, 27, 247, 232, 58, 215, 127, 11, 141, 88, 116, 67, 61, 201, 165, 224, 230, 137, 153, 152, 234, 30, 119, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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