Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6043da011fd304b469a652b383ea2e4950f346673d77a13715768501365b44ca

Tx prefix hash: 519f5c89a61b6867a5a71b6b29511b5dfb8f081f14a268f9d2f5a48f64751294
Tx public key: d86929b7d0dbb4424a56ec6b7336c4464ce43aa0fb128a9b865147f95b98cae1
Timestamp: 1717742886 Timestamp [UCT]: 2024-06-07 06:48:06 Age [y:d:h:m:s]: 00:282:02:58:08
Block: 1038852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201620 RingCT/type: yes/0
Extra: 01d86929b7d0dbb4424a56ec6b7336c4464ce43aa0fb128a9b865147f95b98cae10211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bb03ede6e7c1c2b08f204496a5e54e6e8724045665273ca8c299813f8184f2e 0.600000000000 1507413 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": 1038862, "vin": [ { "gen": { "height": 1038852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bb03ede6e7c1c2b08f204496a5e54e6e8724045665273ca8c299813f8184f2e" } } ], "extra": [ 1, 216, 105, 41, 183, 208, 219, 180, 66, 74, 86, 236, 107, 115, 54, 196, 70, 76, 228, 58, 160, 251, 18, 138, 155, 134, 81, 71, 249, 91, 152, 202, 225, 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