Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f3ecae8eb99e68bec83757cfb19cbf9ac22304fd56b5c4bebb9e4c9439b1fab

Tx prefix hash: 524fe8a508948030ccc4803650a8306eac39ceed34060854d4342ee401be7e82
Tx public key: 8f5d006e79ebf8f1e8f539718cf9de89f821fb8f2d22ca5154c7aea10619e872
Timestamp: 1705027882 Timestamp [UCT]: 2024-01-12 02:51:22 Age [y:d:h:m:s]: 01:327:02:31:21
Block: 933409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492642 RingCT/type: yes/0
Extra: 018f5d006e79ebf8f1e8f539718cf9de89f821fb8f2d22ca5154c7aea10619e8720211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52d965eb5b20a923d16bcae4c73af0a7af92237af4c3241815585453550ce882 0.600000000000 1391371 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": 933419, "vin": [ { "gen": { "height": 933409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52d965eb5b20a923d16bcae4c73af0a7af92237af4c3241815585453550ce882" } } ], "extra": [ 1, 143, 93, 0, 110, 121, 235, 248, 241, 232, 245, 57, 113, 140, 249, 222, 137, 248, 33, 251, 143, 45, 34, 202, 81, 84, 199, 174, 161, 6, 25, 232, 114, 2, 17, 0, 0, 0, 3, 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