Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7de70e3aa2d5abae7156dd677a773abcde1893dc7635738f26f1bb6bfb5a2db

Tx prefix hash: ab4cf6e33da42055325d4d219a8ddbfbe042744d1db94c1ec9e776fff83ec70b
Tx public key: f8a59f338223bf42469833c0f7a3ac4440fb738bd957d94dec402fc35e21f1e8
Timestamp: 1705384858 Timestamp [UCT]: 2024-01-16 06:00:58 Age [y:d:h:m:s]: 01:147:15:14:33
Block: 936356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366644 RingCT/type: yes/0
Extra: 01f8a59f338223bf42469833c0f7a3ac4440fb738bd957d94dec402fc35e21f1e80211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b522e4488a6543c70e61d997d93d17765e942ee97a1c082b2214b8208634d0c 0.600000000000 1394380 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": 936366, "vin": [ { "gen": { "height": 936356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b522e4488a6543c70e61d997d93d17765e942ee97a1c082b2214b8208634d0c" } } ], "extra": [ 1, 248, 165, 159, 51, 130, 35, 191, 66, 70, 152, 51, 192, 247, 163, 172, 68, 64, 251, 115, 139, 217, 87, 217, 77, 236, 64, 47, 195, 94, 33, 241, 232, 2, 17, 0, 0, 0, 8, 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