Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18d81f5380fe8054a917945cb327522dcfc5f7fe1d7201a72a532f2d1f81b447

Tx prefix hash: 942f87514ca393ef9430578f4a05b78880bb04cf930cb03924938d9c3214a5d2
Tx public key: 29fe338f63913ab2c0354f803457a6b6e39589f3bdb4505c3a0f5975dfdef8b9
Timestamp: 1736496744 Timestamp [UCT]: 2025-01-10 08:12:24 Age [y:d:h:m:s]: 00:113:14:30:13
Block: 1194172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80995 RingCT/type: yes/0
Extra: 0129fe338f63913ab2c0354f803457a6b6e39589f3bdb4505c3a0f5975dfdef8b9021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9814e997dd4ba5278ca2bb7a5d358e32b057947bf89c38b56514ab9f15c71f0f 0.600000000000 1680739 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": 1194182, "vin": [ { "gen": { "height": 1194172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9814e997dd4ba5278ca2bb7a5d358e32b057947bf89c38b56514ab9f15c71f0f" } } ], "extra": [ 1, 41, 254, 51, 143, 99, 145, 58, 178, 192, 53, 79, 128, 52, 87, 166, 182, 227, 149, 137, 243, 189, 180, 80, 92, 58, 15, 89, 117, 223, 222, 248, 185, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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