Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b721f212e22348a5953c9b747fa282804e61b850e16f18e0cdd3ea9487307377

Tx prefix hash: 7bfdea07358aae3a068f99a3453c7fe17072803dbf493bf8aaf3d6955ea5d87a
Tx public key: e9ac6307338ea9f4056d8b45f344e61a8237b2df25dae90cdc4424884215cbcd
Timestamp: 1710949986 Timestamp [UCT]: 2024-03-20 15:53:06 Age [y:d:h:m:s]: 01:028:23:00:11
Block: 982549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281666 RingCT/type: yes/0
Extra: 01e9ac6307338ea9f4056d8b45f344e61a8237b2df25dae90cdc4424884215cbcd0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c413ca47bae87d7e6dc458e0e30427d527086a344855d49871f4c038b9312ea5 0.600000000000 1442654 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": 982559, "vin": [ { "gen": { "height": 982549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c413ca47bae87d7e6dc458e0e30427d527086a344855d49871f4c038b9312ea5" } } ], "extra": [ 1, 233, 172, 99, 7, 51, 142, 169, 244, 5, 109, 139, 69, 243, 68, 230, 26, 130, 55, 178, 223, 37, 218, 233, 12, 220, 68, 36, 136, 66, 21, 203, 205, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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