Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ef1cfdb285732974124fb8521af8de425be43fdb0a86d9ff8f52150ec1559ff

Tx prefix hash: c4b5b256901cafcbde7bb2df21e0aa4921217e84d3e19fab4e0e1ede0ae5ad61
Tx public key: 0a51e21bcb25afcf856970a3b4ad683485dd5bce7e60fe49fd1ea0bcff4304d5
Timestamp: 1723269986 Timestamp [UCT]: 2024-08-10 06:06:26 Age [y:d:h:m:s]: 01:089:23:38:17
Block: 1084667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322779 RingCT/type: yes/0
Extra: 010a51e21bcb25afcf856970a3b4ad683485dd5bce7e60fe49fd1ea0bcff4304d502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 501db72816c66bb03183b1f8a44b1e6affd76642d27cccf08fbb0635fd79ca02 0.600000000000 1559026 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": 1084677, "vin": [ { "gen": { "height": 1084667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "501db72816c66bb03183b1f8a44b1e6affd76642d27cccf08fbb0635fd79ca02" } } ], "extra": [ 1, 10, 81, 226, 27, 203, 37, 175, 207, 133, 105, 112, 163, 180, 173, 104, 52, 133, 221, 91, 206, 126, 96, 254, 73, 253, 30, 160, 188, 255, 67, 4, 213, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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