Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfada1f7d808a2c83bbcb966f22f636a86e5cb3ff14d3ab740c540cf236cf509

Tx prefix hash: 1ba8cedfbfd336cbaba9c7ae85a7901e9f83cc54a3b954f31711f78bbbb87145
Tx public key: 09f8cc9e27fdf9c949703b9aa86d2c32387b69192517d12178e46c6b591cac25
Timestamp: 1694864706 Timestamp [UCT]: 2023-09-16 11:45:06 Age [y:d:h:m:s]: 02:046:12:39:09
Block: 849357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552930 RingCT/type: yes/0
Extra: 0109f8cc9e27fdf9c949703b9aa86d2c32387b69192517d12178e46c6b591cac25021100000003faf35c9c000000000000000000

1 output(s) for total of 0.941299291000 dcy

stealth address amount amount idx
00: dc143a0e111ed6eed187e47d5f283499ab0472a634c3a655b0a0d1a4dde69853 0.941299291000 1303017 of 0

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": 849367, "vin": [ { "gen": { "height": 849357 } } ], "vout": [ { "amount": 941299291, "target": { "key": "dc143a0e111ed6eed187e47d5f283499ab0472a634c3a655b0a0d1a4dde69853" } } ], "extra": [ 1, 9, 248, 204, 158, 39, 253, 249, 201, 73, 112, 59, 154, 168, 109, 44, 50, 56, 123, 105, 25, 37, 23, 209, 33, 120, 228, 108, 107, 89, 28, 172, 37, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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