Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 260c3676a465ca81de3d6ea60064f20dd179dc2de7327ef24f7b0cf3071c9538

Tx prefix hash: 5c01a0046fbd4a2525c993f9647eaf7b3e63226758fec0fc9014b313aedaaec8
Tx public key: d65ff2c19776894e92dfe7e634fa0acb62d92250a5f7f7f43fc3b41c20d0a9fd
Timestamp: 1708132388 Timestamp [UCT]: 2024-02-17 01:13:08 Age [y:d:h:m:s]: 01:038:13:26:25
Block: 959163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288573 RingCT/type: yes/0
Extra: 01d65ff2c19776894e92dfe7e634fa0acb62d92250a5f7f7f43fc3b41c20d0a9fd0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3170d3eb482637b3cf4108d62c51fd6578b287417762dc9b894bd8132d8c5b14 0.600000000000 1418694 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": 959173, "vin": [ { "gen": { "height": 959163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3170d3eb482637b3cf4108d62c51fd6578b287417762dc9b894bd8132d8c5b14" } } ], "extra": [ 1, 214, 95, 242, 193, 151, 118, 137, 78, 146, 223, 231, 230, 52, 250, 10, 203, 98, 217, 34, 80, 165, 247, 247, 244, 63, 195, 180, 28, 32, 208, 169, 253, 2, 17, 0, 0, 0, 9, 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