Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8375309cbe2d6e898448ca9d3228dbf3c373861f74f3c6adc1375ef98a6abb0c

Tx prefix hash: 0672d587b95a9fd1202b05ee5d14d39bcec149da993f9e056d36e0c2ce4c09dc
Tx public key: 121e4ce17f619f2cbe059f1ffc2fccc7cfb5ca3c6c7ed3f0ffc1d3de809bd515
Timestamp: 1706482754 Timestamp [UCT]: 2024-01-28 22:59:14 Age [y:d:h:m:s]: 01:063:19:02:55
Block: 945465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306668 RingCT/type: yes/0
Extra: 01121e4ce17f619f2cbe059f1ffc2fccc7cfb5ca3c6c7ed3f0ffc1d3de809bd51502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cb0573cae84e341bc987c06235dc7ae21f8f1949a289a2d7fa892539094e5f9 0.600000000000 1403779 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": 945475, "vin": [ { "gen": { "height": 945465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cb0573cae84e341bc987c06235dc7ae21f8f1949a289a2d7fa892539094e5f9" } } ], "extra": [ 1, 18, 30, 76, 225, 127, 97, 159, 44, 190, 5, 159, 31, 252, 47, 204, 199, 207, 181, 202, 60, 108, 126, 211, 240, 255, 193, 211, 222, 128, 155, 213, 21, 2, 17, 0, 0, 0, 1, 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