Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8ad3d8d1c39529ddc30ed1c2e12e350f002f9f40cd48f1d109a563301a289a6

Tx prefix hash: d70f7e1205386e5c88f82c7be20794258dbadc559c4ffc0ad01a86684649c4c9
Tx public key: 7d77a2211a4c5b7a58dec3311caa117527f71ced44930f05dc1a8076142f4eb4
Timestamp: 1709264560 Timestamp [UCT]: 2024-03-01 03:42:40 Age [y:d:h:m:s]: 01:251:22:40:15
Block: 968561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438787 RingCT/type: yes/0
Extra: 017d77a2211a4c5b7a58dec3311caa117527f71ced44930f05dc1a8076142f4eb402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65d000000a114998d563c2aa5c421b9f0dfe95dcc0dfd5db70a5c898f8cd83f8 0.600000000000 1428378 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": 968571, "vin": [ { "gen": { "height": 968561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65d000000a114998d563c2aa5c421b9f0dfe95dcc0dfd5db70a5c898f8cd83f8" } } ], "extra": [ 1, 125, 119, 162, 33, 26, 76, 91, 122, 88, 222, 195, 49, 28, 170, 17, 117, 39, 247, 28, 237, 68, 147, 15, 5, 220, 26, 128, 118, 20, 47, 78, 180, 2, 17, 0, 0, 0, 2, 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