Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 795716fc8cdedb64db49a7e7480ff014fc4216bc182e171486160846247a41ee

Tx prefix hash: a7361e71e05a62d601f8621dc5bfed87d0ea9d5af5e569dd1dd59f118353fd6d
Tx public key: b2fd800cd6fda90f0c82abafdcb722fc3e76ea841d39b623b7ef968b2216b93b
Timestamp: 1737458590 Timestamp [UCT]: 2025-01-21 11:23:10 Age [y:d:h:m:s]: 00:148:02:45:37
Block: 1202103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105593 RingCT/type: yes/0
Extra: 01b2fd800cd6fda90f0c82abafdcb722fc3e76ea841d39b623b7ef968b2216b93b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60b8764620d90b4793d001cda863c844feee01a05368c95ebc5bf8fb3c6cbf0f 0.600000000000 1688762 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": 1202113, "vin": [ { "gen": { "height": 1202103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60b8764620d90b4793d001cda863c844feee01a05368c95ebc5bf8fb3c6cbf0f" } } ], "extra": [ 1, 178, 253, 128, 12, 214, 253, 169, 15, 12, 130, 171, 175, 220, 183, 34, 252, 62, 118, 234, 132, 29, 57, 182, 35, 183, 239, 150, 139, 34, 22, 185, 59, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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