Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 234ba0ad9dc9687a38af1d8fd9dd6de35464aab797d456043d4f732833383f12

Tx prefix hash: 4d9d1f7352f7a1bd51f54f0870cda47b53b9de692b2010e6094eb368f3a32f78
Tx public key: a2e8b13c9901360c8b397533ae7140e90a49492d38c9ce282cb49c439c57ad7c
Timestamp: 1737426698 Timestamp [UCT]: 2025-01-21 02:31:38 Age [y:d:h:m:s]: 00:053:12:15:25
Block: 1201833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38076 RingCT/type: yes/0
Extra: 01a2e8b13c9901360c8b397533ae7140e90a49492d38c9ce282cb49c439c57ad7c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c6406472dabe67beb3434c730869786fc4ad30c6747e8819abd3f5f323afae8 0.600000000000 1688490 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": 1201843, "vin": [ { "gen": { "height": 1201833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c6406472dabe67beb3434c730869786fc4ad30c6747e8819abd3f5f323afae8" } } ], "extra": [ 1, 162, 232, 177, 60, 153, 1, 54, 12, 139, 57, 117, 51, 174, 113, 64, 233, 10, 73, 73, 45, 56, 201, 206, 40, 44, 180, 156, 67, 156, 87, 173, 124, 2, 17, 0, 0, 0, 1, 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