Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4cea9227e97d6de53d8489055343637f3dbd00615375599ceb1102394a1a3de

Tx prefix hash: 449fbab8f46d8a13511ab8c495a29909647b74d0de853f9ededd3b22c91f1c85
Tx public key: 6c20d611c8d58f32a964f17abea53f095e76057b0d182b65de91d9a527d09a71
Timestamp: 1714507396 Timestamp [UCT]: 2024-04-30 20:03:16 Age [y:d:h:m:s]: 00:341:17:54:55
Block: 1012016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244292 RingCT/type: yes/0
Extra: 016c20d611c8d58f32a964f17abea53f095e76057b0d182b65de91d9a527d09a7102110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8463000778bf852fb2c68a307a62fbdbe56626cc4bdfa3b5f8af137d3dbc7bea 0.600000000000 1474418 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": 1012026, "vin": [ { "gen": { "height": 1012016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8463000778bf852fb2c68a307a62fbdbe56626cc4bdfa3b5f8af137d3dbc7bea" } } ], "extra": [ 1, 108, 32, 214, 17, 200, 213, 143, 50, 169, 100, 241, 122, 190, 165, 63, 9, 94, 118, 5, 123, 13, 24, 43, 101, 222, 145, 217, 165, 39, 208, 154, 113, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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