Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d22024c9cf26baca8b1ae56d1f56ce57b47673c4125ea2f1506926d2b0e8e771

Tx prefix hash: c197fbe59b336c41d6120e7a27faa1d9c470891f8a3ebe347b09c07e05e95e30
Tx public key: a423b0e9b7b80f0e9c6075015a0de496930dd90843e4e4c42f80ae94868a0818
Timestamp: 1643289123 Timestamp [UCT]: 2022-01-27 13:12:03 Age [y:d:h:m:s]: 02:346:02:06:10
Block: 426355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 765901 RingCT/type: yes/0
Extra: 01a423b0e9b7b80f0e9c6075015a0de496930dd90843e4e4c42f80ae94868a0818021100000001c9993c7f000000000000000000

1 output(s) for total of 23.730626832000 dcy

stealth address amount amount idx
00: bead5f93eb09926a12dff9bf41e4efdc5d3f5d3242ba68b3fc5398c3d82dab04 23.730626832000 835172 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": 426365, "vin": [ { "gen": { "height": 426355 } } ], "vout": [ { "amount": 23730626832, "target": { "key": "bead5f93eb09926a12dff9bf41e4efdc5d3f5d3242ba68b3fc5398c3d82dab04" } } ], "extra": [ 1, 164, 35, 176, 233, 183, 184, 15, 14, 156, 96, 117, 1, 90, 13, 228, 150, 147, 13, 217, 8, 67, 228, 228, 196, 47, 128, 174, 148, 134, 138, 8, 24, 2, 17, 0, 0, 0, 1, 201, 153, 60, 127, 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