Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a770ad135235014cd35f44819c025ddaee6bc17c5d33cb033fe1e5a81d8a92a

Tx prefix hash: 2413b5e738de710118c4fe7c6eaa332a77103b1236663cf4b005bfc181d9fffb
Tx public key: 7017cc9345d2fe8f926e391c18152a08b6e918ef20c99cd948c8bce5345c4761
Timestamp: 1710069661 Timestamp [UCT]: 2024-03-10 11:21:01 Age [y:d:h:m:s]: 01:031:01:19:50
Block: 975238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283184 RingCT/type: yes/0
Extra: 017017cc9345d2fe8f926e391c18152a08b6e918ef20c99cd948c8bce5345c476102110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d62e17b071a7e41f40c54b652ebe938cb2aad2b8b9365c1fdf71336c37bb6d2 0.600000000000 1435209 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": 975248, "vin": [ { "gen": { "height": 975238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d62e17b071a7e41f40c54b652ebe938cb2aad2b8b9365c1fdf71336c37bb6d2" } } ], "extra": [ 1, 112, 23, 204, 147, 69, 210, 254, 143, 146, 110, 57, 28, 24, 21, 42, 8, 182, 233, 24, 239, 32, 201, 156, 217, 72, 200, 188, 229, 52, 92, 71, 97, 2, 17, 0, 0, 0, 10, 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