Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dae59d9e5bf672342844209ac4fb1384a54378580d3c64d6e25d111216e6ce38

Tx prefix hash: 4d45283e77af2310491dfbb9bf80b87c515414ef32ec5964f3a6c1143b98987d
Tx public key: 1a4c78f851ee3a6302a7acfa60c7bf3655893402d0d2dc76338a2c3b370fd1d1
Timestamp: 1709116346 Timestamp [UCT]: 2024-02-28 10:32:26 Age [y:d:h:m:s]: 00:259:00:34:42
Block: 967338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185436 RingCT/type: yes/0
Extra: 011a4c78f851ee3a6302a7acfa60c7bf3655893402d0d2dc76338a2c3b370fd1d102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74ea09ce166a5e49de567f241558de16f902ad08470416e2b5c3d80ed3604cdf 0.600000000000 1427115 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": 967348, "vin": [ { "gen": { "height": 967338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74ea09ce166a5e49de567f241558de16f902ad08470416e2b5c3d80ed3604cdf" } } ], "extra": [ 1, 26, 76, 120, 248, 81, 238, 58, 99, 2, 167, 172, 250, 96, 199, 191, 54, 85, 137, 52, 2, 208, 210, 220, 118, 51, 138, 44, 59, 55, 15, 209, 209, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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