Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13bbd038f17ed4bb3a0280dcaa4e4509fc97c9912af490811da61ec8c0b0a202

Tx prefix hash: 90e5a14b7aa2a3a08b38969aebf44aadba70f9964c66b294247e1a3d62b21383
Tx public key: 0f61ae4d643cfe0b1df9e3eaf304a4bed65db5109cf0902efbba2f76f0ee651a
Timestamp: 1702222334 Timestamp [UCT]: 2023-12-10 15:32:14 Age [y:d:h:m:s]: 01:144:02:35:06
Block: 910166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364159 RingCT/type: yes/0
Extra: 010f61ae4d643cfe0b1df9e3eaf304a4bed65db5109cf0902efbba2f76f0ee651a02110000000afaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cd7915e3fed88783f4ddcfa1d47846f0076e5ea36e1dd3f6834a7adc9c6b0e7 0.600000000000 1367311 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": 910176, "vin": [ { "gen": { "height": 910166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd7915e3fed88783f4ddcfa1d47846f0076e5ea36e1dd3f6834a7adc9c6b0e7" } } ], "extra": [ 1, 15, 97, 174, 77, 100, 60, 254, 11, 29, 249, 227, 234, 243, 4, 164, 190, 214, 93, 181, 16, 156, 240, 144, 46, 251, 186, 47, 118, 240, 238, 101, 26, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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