Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5351289f316bafcddde1dd08b94b999c6cdad7bb8b5ae195497439f1eb5046d6

Tx prefix hash: 2f5b34e18d4f9146d43537e14301185d780941f7c56a6a13533d5d6c83164e3e
Tx public key: f61d0a47fc0e3a28b5b0990f528787c847dc212b6d23a4fd8cbaa8e7bbddcb74
Timestamp: 1709365556 Timestamp [UCT]: 2024-03-02 07:45:56 Age [y:d:h:m:s]: 01:037:23:30:33
Block: 969405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288140 RingCT/type: yes/0
Extra: 01f61d0a47fc0e3a28b5b0990f528787c847dc212b6d23a4fd8cbaa8e7bbddcb740211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d95d115c6e6823666cf6cd1a4db00872e6234a1189309731698755e420314ce 0.600000000000 1429234 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": 969415, "vin": [ { "gen": { "height": 969405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d95d115c6e6823666cf6cd1a4db00872e6234a1189309731698755e420314ce" } } ], "extra": [ 1, 246, 29, 10, 71, 252, 14, 58, 40, 181, 176, 153, 15, 82, 135, 135, 200, 71, 220, 33, 43, 109, 35, 164, 253, 140, 186, 168, 231, 187, 221, 203, 116, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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