Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fb59bb2991ef96fce7fb277ce2b60b55712e0cc89c03ddcccc9f20c2ce7f998

Tx prefix hash: 5c1882fa450a205188b0a8f816447997f110b9def2e0881d841ea713cc91f60f
Tx public key: 7fe2198d76f8f55f217877081e3ed67f1e106b2ddc70fe0226ae5c2c23122220
Timestamp: 1708062169 Timestamp [UCT]: 2024-02-16 05:42:49 Age [y:d:h:m:s]: 00:331:20:53:20
Block: 958578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237580 RingCT/type: yes/0
Extra: 017fe2198d76f8f55f217877081e3ed67f1e106b2ddc70fe0226ae5c2c231222200211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5466c06b7eeacb058fed0bc97f00a85ef51a630a659b5ff9539b4dfcb1b4ddeb 0.600000000000 1417937 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": 958588, "vin": [ { "gen": { "height": 958578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5466c06b7eeacb058fed0bc97f00a85ef51a630a659b5ff9539b4dfcb1b4ddeb" } } ], "extra": [ 1, 127, 226, 25, 141, 118, 248, 245, 95, 33, 120, 119, 8, 30, 62, 214, 127, 30, 16, 107, 45, 220, 112, 254, 2, 38, 174, 92, 44, 35, 18, 34, 32, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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