Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7e3abaa1f4d0b2784c1e0c2f8ce298bc4bb8982b2e2446ae2142b419966ebd

Tx prefix hash: 7390038374a5d5a636a9d0caa6b5821975ff7528263219536d5ae5722d91ff5b
Tx public key: a600793846f0594f6f92f9a1449cbdf81495563e132db820e45c5960c068abf5
Timestamp: 1713039708 Timestamp [UCT]: 2024-04-13 20:21:48 Age [y:d:h:m:s]: 01:208:11:43:05
Block: 999827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407693 RingCT/type: yes/0
Extra: 01a600793846f0594f6f92f9a1449cbdf81495563e132db820e45c5960c068abf5021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0b44192af0b7c8e94d5633f33c9c471f5b817716e6111ca433735741a259360 0.600000000000 1460313 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": 999837, "vin": [ { "gen": { "height": 999827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b44192af0b7c8e94d5633f33c9c471f5b817716e6111ca433735741a259360" } } ], "extra": [ 1, 166, 0, 121, 56, 70, 240, 89, 79, 111, 146, 249, 161, 68, 156, 189, 248, 20, 149, 86, 62, 19, 45, 184, 32, 228, 92, 89, 96, 192, 104, 171, 245, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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