Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0fbd65bcf5ebbb68dca793c6b9c61ffdf2f033c7112fa4d89ad20c35d7b0164

Tx prefix hash: f1d3fa581043c2419dfde6d989f8e97af44cfac71e16eb44937a993c7deb64e2
Tx public key: 2d64db70e5339da3cbd44a929798f3105f82085a806b011103e11b9825cd50ee
Timestamp: 1738014007 Timestamp [UCT]: 2025-01-27 21:40:07 Age [y:d:h:m:s]: 00:045:18:25:16
Block: 1206500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32733 RingCT/type: yes/0
Extra: 012d64db70e5339da3cbd44a929798f3105f82085a806b011103e11b9825cd50ee0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6009f03b9f038dc29258f0e5a3e3b3634b1e78c269623ccf6eb5aad0566a81c4 0.600000000000 1693209 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": 1206510, "vin": [ { "gen": { "height": 1206500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6009f03b9f038dc29258f0e5a3e3b3634b1e78c269623ccf6eb5aad0566a81c4" } } ], "extra": [ 1, 45, 100, 219, 112, 229, 51, 157, 163, 203, 212, 74, 146, 151, 152, 243, 16, 95, 130, 8, 90, 128, 107, 1, 17, 3, 225, 27, 152, 37, 205, 80, 238, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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