Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f752bba3ae028f97035b853e78b5d15a007272143046b2c59aca17be7309f81b

Tx prefix hash: b2967f78ef0a07a05b8a2c42647ea5668e3c4bfa6adb2b4ff4aaa1d6a650585d
Tx public key: 2b473fb2fd81309798d6599212e68d5ed280e0d404619366390ff903f9dec555
Timestamp: 1711443058 Timestamp [UCT]: 2024-03-26 08:50:58 Age [y:d:h:m:s]: 00:250:02:06:03
Block: 986636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179023 RingCT/type: yes/0
Extra: 012b473fb2fd81309798d6599212e68d5ed280e0d404619366390ff903f9dec555021100000001a162b83d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75e96faa797a0b427da3c0e87fdd8ba96657e4abe3bc9f0dee6f48ec5ef0cd1f 0.600000000000 1446867 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": 986646, "vin": [ { "gen": { "height": 986636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75e96faa797a0b427da3c0e87fdd8ba96657e4abe3bc9f0dee6f48ec5ef0cd1f" } } ], "extra": [ 1, 43, 71, 63, 178, 253, 129, 48, 151, 152, 214, 89, 146, 18, 230, 141, 94, 210, 128, 224, 212, 4, 97, 147, 102, 57, 15, 249, 3, 249, 222, 197, 85, 2, 17, 0, 0, 0, 1, 161, 98, 184, 61, 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