Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a92edee10845199cf824f3a5fc3662c29e6f0dba1c5c15553cd25fd8103dc7

Tx prefix hash: f40d8ed924729d8f42f84f0a74570a130b4359e45f4840c41021190b734e5723
Tx public key: 97711e97fd00e9c88644bb63b070d0ce1b6987f79d9faf75822ab2741f83dc17
Timestamp: 1709663159 Timestamp [UCT]: 2024-03-05 18:25:59 Age [y:d:h:m:s]: 00:327:11:04:16
Block: 971863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234159 RingCT/type: yes/0
Extra: 0197711e97fd00e9c88644bb63b070d0ce1b6987f79d9faf75822ab2741f83dc170211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bf8bcbd646fe817a127609de19d6d2efa02aa5b1d66c46e8c51deef40e8fd7f 0.600000000000 1431766 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": 971873, "vin": [ { "gen": { "height": 971863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bf8bcbd646fe817a127609de19d6d2efa02aa5b1d66c46e8c51deef40e8fd7f" } } ], "extra": [ 1, 151, 113, 30, 151, 253, 0, 233, 200, 134, 68, 187, 99, 176, 112, 208, 206, 27, 105, 135, 247, 157, 159, 175, 117, 130, 42, 178, 116, 31, 131, 220, 23, 2, 17, 0, 0, 0, 2, 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