Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0eb417c24c3b1bebca00681517c28dac9e22b719d5464c511dcb535891c3d4e

Tx prefix hash: d87b7806eba0b11db4b5c346c7ab6da5755dc0da880f64f4439950416cfd2b7a
Tx public key: a8b53e8ae790410e51757d6b53fb5216e310e0e5d489a371a60ab3d1b86fccc5
Timestamp: 1704479486 Timestamp [UCT]: 2024-01-05 18:31:26 Age [y:d:h:m:s]: 01:319:05:32:25
Block: 928870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486996 RingCT/type: yes/0
Extra: 01a8b53e8ae790410e51757d6b53fb5216e310e0e5d489a371a60ab3d1b86fccc50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa84b28ed7dd43d8de6a881f5ccf6461200e5deffd68940963146d35120e62a4 0.600000000000 1386734 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": 928880, "vin": [ { "gen": { "height": 928870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa84b28ed7dd43d8de6a881f5ccf6461200e5deffd68940963146d35120e62a4" } } ], "extra": [ 1, 168, 181, 62, 138, 231, 144, 65, 14, 81, 117, 125, 107, 83, 251, 82, 22, 227, 16, 224, 229, 212, 137, 163, 113, 166, 10, 179, 209, 184, 111, 204, 197, 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