Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08a70d883c6900a26cdf11ca35ec1c9b86583cb3fe1ab776ba729c15088bb537

Tx prefix hash: a50ada95a606131f1a0b1b845a1415760b70db5b037c7e84ef04b25dd87f28a2
Tx public key: f67f6860bdc28dd7797d2613e6f8d8a7e350eafef9dce144c1b57249ce2964b6
Timestamp: 1733948240 Timestamp [UCT]: 2024-12-11 20:17:20 Age [y:d:h:m:s]: 00:095:16:13:12
Block: 1173101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68168 RingCT/type: yes/0
Extra: 01f67f6860bdc28dd7797d2613e6f8d8a7e350eafef9dce144c1b57249ce2964b60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21da0120e1dd2df808918a83c3af9df0555b166a8c7c399f877fc49fa324e373 0.600000000000 1659082 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": 1173111, "vin": [ { "gen": { "height": 1173101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21da0120e1dd2df808918a83c3af9df0555b166a8c7c399f877fc49fa324e373" } } ], "extra": [ 1, 246, 127, 104, 96, 189, 194, 141, 215, 121, 125, 38, 19, 230, 248, 216, 167, 227, 80, 234, 254, 249, 220, 225, 68, 193, 181, 114, 73, 206, 41, 100, 182, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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