Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f011b673b25643469660d279cbbb7f61343462bc8141c0c8a229cfa4a14ae7b

Tx prefix hash: 6c0805d74b6b6839a9a0477c39d77d981cca84cb0274e27e8d32baed4a2772e0
Tx public key: 2fa93e02af6e32d8f87d9134ac9f7cb86858c09619400c31f3e64c5a7cb28d82
Timestamp: 1722979371 Timestamp [UCT]: 2024-08-06 21:22:51 Age [y:d:h:m:s]: 00:109:04:31:19
Block: 1082246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78132 RingCT/type: yes/0
Extra: 012fa93e02af6e32d8f87d9134ac9f7cb86858c09619400c31f3e64c5a7cb28d82021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e11450ce472e76750fb5776ef6742e513f74baec456d69dcf48392a623910f 0.600000000000 1556071 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": 1082256, "vin": [ { "gen": { "height": 1082246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e11450ce472e76750fb5776ef6742e513f74baec456d69dcf48392a623910f" } } ], "extra": [ 1, 47, 169, 62, 2, 175, 110, 50, 216, 248, 125, 145, 52, 172, 159, 124, 184, 104, 88, 192, 150, 25, 64, 12, 49, 243, 230, 76, 90, 124, 178, 141, 130, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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