Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97165fd8bccd2724fd024deaec9616a79f0c0ca97d6c1bfa3976c7386d9d63e9

Tx prefix hash: f2904842995f8274d7fa05e595435df01e6ed179c78c517b3475bb069e844cc8
Tx public key: 8f3e69120150c4a49a49c02fd78f7662ef78df8e13af50924f3847f2f952abd6
Timestamp: 1713011659 Timestamp [UCT]: 2024-04-13 12:34:19 Age [y:d:h:m:s]: 01:248:03:45:47
Block: 999604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436082 RingCT/type: yes/0
Extra: 018f3e69120150c4a49a49c02fd78f7662ef78df8e13af50924f3847f2f952abd602110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba3ce467db9588a80f288476a0f6f7435c42e2cc203c094369b0fd855000b45c 0.600000000000 1460086 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": 999614, "vin": [ { "gen": { "height": 999604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba3ce467db9588a80f288476a0f6f7435c42e2cc203c094369b0fd855000b45c" } } ], "extra": [ 1, 143, 62, 105, 18, 1, 80, 196, 164, 154, 73, 192, 47, 215, 143, 118, 98, 239, 120, 223, 142, 19, 175, 80, 146, 79, 56, 71, 242, 249, 82, 171, 214, 2, 17, 0, 0, 0, 16, 89, 218, 211, 245, 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