Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3da8f4b4777bc20ddc40e339cf66f9b5ecc48a773a7586acf08f350fe81d76e6

Tx prefix hash: 15740214a88b5c58eca17d3bc6b4bafc8d8f5d32e86239649ffc7df30a796bd8
Tx public key: 37764c4ad8fa18a80288b747fa88142f7ecb15e5b236f5bcf1eb38f1e44f759f
Timestamp: 1729963029 Timestamp [UCT]: 2024-10-26 17:17:09 Age [y:d:h:m:s]: 00:155:20:01:41
Block: 1140124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111164 RingCT/type: yes/0
Extra: 0137764c4ad8fa18a80288b747fa88142f7ecb15e5b236f5bcf1eb38f1e44f759f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1471e2494a85ecddf896275b340164c8d54ec407e006d9ef37c3240506c2d38b 0.600000000000 1623919 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": 1140134, "vin": [ { "gen": { "height": 1140124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1471e2494a85ecddf896275b340164c8d54ec407e006d9ef37c3240506c2d38b" } } ], "extra": [ 1, 55, 118, 76, 74, 216, 250, 24, 168, 2, 136, 183, 71, 250, 136, 20, 47, 126, 203, 21, 229, 178, 54, 245, 188, 241, 235, 56, 241, 228, 79, 117, 159, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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