Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c495028a7617a4c6f87f491c488475fc1ced78da5166e0b7f85b6b65b1a73d2

Tx prefix hash: e1d289d8774aba1e50430aff58902d267199e014afac1a481ac6fd8cb7bc6419
Tx public key: a6305f445184f44a057b6c22a4d2a736caaf6acf21a988f7168ad59f230a88a5
Timestamp: 1713278648 Timestamp [UCT]: 2024-04-16 14:44:08 Age [y:d:h:m:s]: 00:353:16:28:17
Block: 1001813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252870 RingCT/type: yes/0
Extra: 01a6305f445184f44a057b6c22a4d2a736caaf6acf21a988f7168ad59f230a88a502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3a563a9286f484b7fbe564bb6d7bcfdcbf45e094327381a01c305ad36393759 0.600000000000 1462325 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": 1001823, "vin": [ { "gen": { "height": 1001813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3a563a9286f484b7fbe564bb6d7bcfdcbf45e094327381a01c305ad36393759" } } ], "extra": [ 1, 166, 48, 95, 68, 81, 132, 244, 74, 5, 123, 108, 34, 164, 210, 167, 54, 202, 175, 106, 207, 33, 169, 136, 247, 22, 138, 213, 159, 35, 10, 136, 165, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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