Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6195c5617dea1bd4883c48c365cc8019fc7783531b501c643dd3262e5d1087c8

Tx prefix hash: e371c79b3af539f3b0b2d43ff98631eccd980e74b20ac9fdcdc0a2e6031a9212
Tx public key: 73d81735a3d8e6387fbce0ac8949568cfb60d7d86dae90f3f024309108c80a1b
Timestamp: 1710959407 Timestamp [UCT]: 2024-03-20 18:30:07 Age [y:d:h:m:s]: 01:062:11:41:14
Block: 982623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305654 RingCT/type: yes/0
Extra: 0173d81735a3d8e6387fbce0ac8949568cfb60d7d86dae90f3f024309108c80a1b02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd08472737347d2caa5e4bfeeccb54f015910d851a399ea9f5c900529e24411c 0.600000000000 1442732 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": 982633, "vin": [ { "gen": { "height": 982623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd08472737347d2caa5e4bfeeccb54f015910d851a399ea9f5c900529e24411c" } } ], "extra": [ 1, 115, 216, 23, 53, 163, 216, 230, 56, 127, 188, 224, 172, 137, 73, 86, 140, 251, 96, 215, 216, 109, 174, 144, 243, 240, 36, 48, 145, 8, 200, 10, 27, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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