Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84f7662c02850703434e8a4f3cd558b94d0111c727211cf0f826a60df8a8923

Tx prefix hash: f95c3bf31664b1fd829faa23a0143c4aa59515da1b5842b36846f3928559ecf4
Tx public key: 00b66ee277a856b5763b46e651fa472a07fc25baea60b99240224c04f16e83a9
Timestamp: 1649630703 Timestamp [UCT]: 2022-04-10 22:45:03 Age [y:d:h:m:s]: 02:211:10:05:24
Block: 477564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 670855 RingCT/type: yes/0
Extra: 0100b66ee277a856b5763b46e651fa472a07fc25baea60b99240224c04f16e83a902110000001aa8c141c5000000000000000000

1 output(s) for total of 16.055818871000 dcy

stealth address amount amount idx
00: 6681a9a65f3ccc85ae09d15384f858fd40eac2424ac27e863ff82afc2de9c71f 16.055818871000 898235 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": 477574, "vin": [ { "gen": { "height": 477564 } } ], "vout": [ { "amount": 16055818871, "target": { "key": "6681a9a65f3ccc85ae09d15384f858fd40eac2424ac27e863ff82afc2de9c71f" } } ], "extra": [ 1, 0, 182, 110, 226, 119, 168, 86, 181, 118, 59, 70, 230, 81, 250, 71, 42, 7, 252, 37, 186, 234, 96, 185, 146, 64, 34, 76, 4, 241, 110, 131, 169, 2, 17, 0, 0, 0, 26, 168, 193, 65, 197, 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