Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6961cfbadb7eb9833c249f14680e81dac291c515adc6306d9058aa2d3fcba25

Tx prefix hash: e8ab579873cd4adfcf0f6d8d367e2e14bdf94c0d20138a9021f66753ef3d10c8
Tx public key: 319bebd9773488c1696ff49fd435e4cfbd22c518356fdc859c6ed6ceec91bd9d
Timestamp: 1720641946 Timestamp [UCT]: 2024-07-10 20:05:46 Age [y:d:h:m:s]: 00:272:00:04:45
Block: 1062881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194325 RingCT/type: yes/0
Extra: 01319bebd9773488c1696ff49fd435e4cfbd22c518356fdc859c6ed6ceec91bd9d021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8ab8f4e86875aac8eb45e424a8483d9da89a26d02e3e2abd3893df46f029b43 0.600000000000 1533392 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": 1062891, "vin": [ { "gen": { "height": 1062881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8ab8f4e86875aac8eb45e424a8483d9da89a26d02e3e2abd3893df46f029b43" } } ], "extra": [ 1, 49, 155, 235, 217, 119, 52, 136, 193, 105, 111, 244, 159, 212, 53, 228, 207, 189, 34, 197, 24, 53, 111, 220, 133, 156, 110, 214, 206, 236, 145, 189, 157, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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