Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e75a6851bfc42677979c797b713ee9367672adb44ff122a499adc84249d35c

Tx prefix hash: 33c95b24e8975a2cac17352225bf78335128c1e8ebf0148a70d8a3166ec55444
Tx public key: 0dce9f3c1cccafb9a9dfa09d01f635be6258f4ec22741516e2a33b1dceb1ac75
Timestamp: 1718881178 Timestamp [UCT]: 2024-06-20 10:59:38 Age [y:d:h:m:s]: 00:278:05:25:49
Block: 1048279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198807 RingCT/type: yes/0
Extra: 010dce9f3c1cccafb9a9dfa09d01f635be6258f4ec22741516e2a33b1dceb1ac750211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4202d2e692c20b6e86ed05a09d58836f38c42de7c09ce61313b2b46a2b79d588 0.600000000000 1518324 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": 1048289, "vin": [ { "gen": { "height": 1048279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4202d2e692c20b6e86ed05a09d58836f38c42de7c09ce61313b2b46a2b79d588" } } ], "extra": [ 1, 13, 206, 159, 60, 28, 204, 175, 185, 169, 223, 160, 157, 1, 246, 53, 190, 98, 88, 244, 236, 34, 116, 21, 22, 226, 163, 59, 29, 206, 177, 172, 117, 2, 17, 0, 0, 0, 2, 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