Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d65c674dcea4870e8054af6185f5770f42e1e35c0e02a4a91810bfedc24b03da

Tx prefix hash: bfd05938a95c2d2e480ae749940f995681ad3d731a8290cc6a0e60a7c7e44184
Tx public key: 74e511df8a8baeff6c7fd3a751c26e5bbd24024ea58c30b7f2f39fb2df287ee2
Timestamp: 1760415885 Timestamp [UCT]: 2025-10-14 04:24:45 Age [y:d:h:m:s]: 00:038:19:57:15
Block: 1389515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27792 RingCT/type: yes/0
Extra: 0174e511df8a8baeff6c7fd3a751c26e5bbd24024ea58c30b7f2f39fb2df287ee202110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d0c16ff3bb02cc6de59af278ee18db4e077aa34317aaf04d818c18b723922f1 0.600000000000 1877744 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": 1389525, "vin": [ { "gen": { "height": 1389515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d0c16ff3bb02cc6de59af278ee18db4e077aa34317aaf04d818c18b723922f1" } } ], "extra": [ 1, 116, 229, 17, 223, 138, 139, 174, 255, 108, 127, 211, 167, 81, 194, 110, 91, 189, 36, 2, 78, 165, 140, 48, 183, 242, 243, 159, 178, 223, 40, 126, 226, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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