Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b02dcaaccd69d7446514e83b274a13c88c32ce1c22b3cd474cc7160f0d3ccf7

Tx prefix hash: 15ed9ca7d222fafe7ab837690a2fa36991af7e5b4f6f264cb2aed07f21632caa
Tx public key: 6acd7c7d27ad3e9d7dc9b152768f91798281f4eec0bd767c56939c47bf30d97e
Timestamp: 1705745491 Timestamp [UCT]: 2024-01-20 10:11:31 Age [y:d:h:m:s]: 01:004:22:33:17
Block: 939349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264820 RingCT/type: yes/0
Extra: 016acd7c7d27ad3e9d7dc9b152768f91798281f4eec0bd767c56939c47bf30d97e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3069e42f556f4cb5b7ae0c548aabe9caa63a1d0c614ad549ff0a5d57989c1461 0.600000000000 1397443 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": 939359, "vin": [ { "gen": { "height": 939349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3069e42f556f4cb5b7ae0c548aabe9caa63a1d0c614ad549ff0a5d57989c1461" } } ], "extra": [ 1, 106, 205, 124, 125, 39, 173, 62, 157, 125, 201, 177, 82, 118, 143, 145, 121, 130, 129, 244, 238, 192, 189, 118, 124, 86, 147, 156, 71, 191, 48, 217, 126, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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