Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ece58308ede14e9fe16db6cb782977d6f65cb2a6560b4a60a1b6e9d2f92ed86c

Tx prefix hash: c42c7dc321236e67247c33827d81114eeb13c76db0e75ab845c8d98c55fa7bb1
Tx public key: 04a05e1fe652861260863e165a485033b399bfeee451ba3fb68be042110b3f0e
Timestamp: 1709838296 Timestamp [UCT]: 2024-03-07 19:04:56 Age [y:d:h:m:s]: 01:030:00:47:56
Block: 973323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282441 RingCT/type: yes/0
Extra: 0104a05e1fe652861260863e165a485033b399bfeee451ba3fb68be042110b3f0e02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 904a01325d9a85878426a55df549e5216fe5fa3c08ffc4f80991073bef84e001 0.600000000000 1433258 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": 973333, "vin": [ { "gen": { "height": 973323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "904a01325d9a85878426a55df549e5216fe5fa3c08ffc4f80991073bef84e001" } } ], "extra": [ 1, 4, 160, 94, 31, 230, 82, 134, 18, 96, 134, 62, 22, 90, 72, 80, 51, 179, 153, 191, 238, 228, 81, 186, 63, 182, 139, 224, 66, 17, 11, 63, 14, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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