Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40e413698fec908ca0a24a9407b6ad645f7bb96ffa98dfe6e714535711304f31

Tx prefix hash: f658ed8b638144de82666312ab505b3c570da35c5f0791b7039753d677ea7a5a
Tx public key: caaa6c6a7d8733e3366c9a56f39f8347257f8d72e207b158217f89d0f6d629bb
Timestamp: 1717634775 Timestamp [UCT]: 2024-06-06 00:46:15 Age [y:d:h:m:s]: 00:282:22:32:05
Block: 1037949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202223 RingCT/type: yes/0
Extra: 01caaa6c6a7d8733e3366c9a56f39f8347257f8d72e207b158217f89d0f6d629bb0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7db66fdb1ca75bb974e131c5a2244252bdfecd9cf2e7facdfdea0a050ed408cc 0.600000000000 1506508 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": 1037959, "vin": [ { "gen": { "height": 1037949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7db66fdb1ca75bb974e131c5a2244252bdfecd9cf2e7facdfdea0a050ed408cc" } } ], "extra": [ 1, 202, 170, 108, 106, 125, 135, 51, 227, 54, 108, 154, 86, 243, 159, 131, 71, 37, 127, 141, 114, 226, 7, 177, 88, 33, 127, 137, 208, 246, 214, 41, 187, 2, 17, 0, 0, 0, 8, 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