Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a3cb8b2613544e4787c9a33aca8a8239a5273591a7ed64650317638a9a36b73

Tx prefix hash: 64167854d00cc91c273ab2824086f64ddc053989ea289aaa9b87f9d5229278a8
Tx public key: 2f26a8c67b297660c1f1592fc3bbdaf5c9533d0e1e479538e07ee8b1bb8d8ff7
Timestamp: 1728148225 Timestamp [UCT]: 2024-10-05 17:10:25 Age [y:d:h:m:s]: 00:223:14:43:54
Block: 1125110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159638 RingCT/type: yes/0
Extra: 012f26a8c67b297660c1f1592fc3bbdaf5c9533d0e1e479538e07ee8b1bb8d8ff702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d4de89e504c3e268123db78d0bc8a52824c9f8e193fefbf28d891a534a93181 0.600000000000 1607783 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": 1125120, "vin": [ { "gen": { "height": 1125110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d4de89e504c3e268123db78d0bc8a52824c9f8e193fefbf28d891a534a93181" } } ], "extra": [ 1, 47, 38, 168, 198, 123, 41, 118, 96, 193, 241, 89, 47, 195, 187, 218, 245, 201, 83, 61, 14, 30, 71, 149, 56, 224, 126, 232, 177, 187, 141, 143, 247, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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