Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ca6b8c5a71e0a3d9b9d6f73bfd85ccdebfccee323fd4402d7e31a3dc4964832

Tx prefix hash: dfa970664bad0a1faadb75548dd1a21cfbc8f64ca5b28391397cff0c90360c4a
Tx public key: ef55eba41c11df0e4421159d543ce493d090f0d4c20297b51df55f5400011b8b
Timestamp: 1734701256 Timestamp [UCT]: 2024-12-20 13:27:36 Age [y:d:h:m:s]: 00:093:13:04:53
Block: 1179350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66602 RingCT/type: yes/0
Extra: 01ef55eba41c11df0e4421159d543ce493d090f0d4c20297b51df55f5400011b8b02110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26911d5b37910114f820f0a54e75c2dfe76f5379292c421917bd28a1821425fb 0.600000000000 1665745 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": 1179360, "vin": [ { "gen": { "height": 1179350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26911d5b37910114f820f0a54e75c2dfe76f5379292c421917bd28a1821425fb" } } ], "extra": [ 1, 239, 85, 235, 164, 28, 17, 223, 14, 68, 33, 21, 157, 84, 60, 228, 147, 208, 144, 240, 212, 194, 2, 151, 181, 29, 245, 95, 84, 0, 1, 27, 139, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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