Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ade89c19910f79e07ab5ccf5f4faf1ba1d9b95d91476e48a1baff80a4500ee2

Tx prefix hash: 10de9791c50625ca1c6d8c8c8805bf3060f0d2078e0658c52f289fdc0aee3359
Tx public key: ad21dd8305f8ca570f3b88b3ae1a68cc434927b3d9f217d1d01a72235e7a9f8d
Timestamp: 1706471962 Timestamp [UCT]: 2024-01-28 19:59:22 Age [y:d:h:m:s]: 01:084:17:38:16
Block: 945379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321658 RingCT/type: yes/0
Extra: 01ad21dd8305f8ca570f3b88b3ae1a68cc434927b3d9f217d1d01a72235e7a9f8d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d59ed1822726c8cf5691fd499d623e1cdc372ddd4837bcc89d6a3a92fdf432b 0.600000000000 1403691 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": 945389, "vin": [ { "gen": { "height": 945379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d59ed1822726c8cf5691fd499d623e1cdc372ddd4837bcc89d6a3a92fdf432b" } } ], "extra": [ 1, 173, 33, 221, 131, 5, 248, 202, 87, 15, 59, 136, 179, 174, 26, 104, 204, 67, 73, 39, 179, 217, 242, 23, 209, 208, 26, 114, 35, 94, 122, 159, 141, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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