Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad1db1efe39d5757fd0180d405f193aefda05c6f05a058938ca7a711e15c84d2

Tx prefix hash: 01419ca31e0d04521d8e051d5fc0ae750b63d66d8ff68f48fc5ac2e1f4875c0f
Tx public key: 4f53ae20496a7eee2f9b6a3bf4d1b3066113256e8c67f6ff09e249185048d454
Timestamp: 1710541014 Timestamp [UCT]: 2024-03-15 22:16:54 Age [y:d:h:m:s]: 01:072:20:18:43
Block: 979153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313072 RingCT/type: yes/0
Extra: 014f53ae20496a7eee2f9b6a3bf4d1b3066113256e8c67f6ff09e249185048d4540211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d413b5224bd792d31cc9eacfce7d089751c498963bdb09ed2375dc84326cfb1d 0.600000000000 1439186 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": 979163, "vin": [ { "gen": { "height": 979153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d413b5224bd792d31cc9eacfce7d089751c498963bdb09ed2375dc84326cfb1d" } } ], "extra": [ 1, 79, 83, 174, 32, 73, 106, 126, 238, 47, 155, 106, 59, 244, 209, 179, 6, 97, 19, 37, 110, 140, 103, 246, 255, 9, 226, 73, 24, 80, 72, 212, 84, 2, 17, 0, 0, 0, 2, 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