Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 314b8066d43523ca50f160adf6992cbf42304363fe22329faf2c2237e7c28c4e

Tx prefix hash: 2813608110b7a028033f3e94bacaf275d81daab1a8b1f451cd1e9248ade23317
Tx public key: d1df90683979ca61ae8fcbd6ef87a8866c17b9e314f8ef67cf3620a5dbe23444
Timestamp: 1645425800 Timestamp [UCT]: 2022-02-21 06:43:20 Age [y:d:h:m:s]: 02:352:11:06:14
Block: 443168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 771068 RingCT/type: yes/0
Extra: 01d1df90683979ca61ae8fcbd6ef87a8866c17b9e314f8ef67cf3620a5dbe23444021100000009a8c141c5000000000000000000

1 output(s) for total of 20.873762461000 dcy

stealth address amount amount idx
00: da0f40d8019df5419380fb4c19adebba9d8d89bf6bfae001e3274a5df1b55e88 20.873762461000 856127 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": 443178, "vin": [ { "gen": { "height": 443168 } } ], "vout": [ { "amount": 20873762461, "target": { "key": "da0f40d8019df5419380fb4c19adebba9d8d89bf6bfae001e3274a5df1b55e88" } } ], "extra": [ 1, 209, 223, 144, 104, 57, 121, 202, 97, 174, 143, 203, 214, 239, 135, 168, 134, 108, 23, 185, 227, 20, 248, 239, 103, 207, 54, 32, 165, 219, 226, 52, 68, 2, 17, 0, 0, 0, 9, 168, 193, 65, 197, 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