Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c94e9359baf6da0e6e85bd43f77fa1cee105a035dd80d0952cb5075a8a2cbe6

Tx prefix hash: e89f10a8659ce1768a094157a50bb880e7db8b863eb0019eb107cf571c854cb6
Tx public key: a01eaa6bef59cd7097ce2dfeb263883cf2725dbb3033e8fa50c25a377017d7e5
Timestamp: 1712991482 Timestamp [UCT]: 2024-04-13 06:58:02 Age [y:d:h:m:s]: 00:315:11:27:39
Block: 999431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225524 RingCT/type: yes/0
Extra: 01a01eaa6bef59cd7097ce2dfeb263883cf2725dbb3033e8fa50c25a377017d7e50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9891154a488b169cb9d218b9d9f21340cdc2673002f92e6b89121c266e7319ca 0.600000000000 1459911 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": 999441, "vin": [ { "gen": { "height": 999431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9891154a488b169cb9d218b9d9f21340cdc2673002f92e6b89121c266e7319ca" } } ], "extra": [ 1, 160, 30, 170, 107, 239, 89, 205, 112, 151, 206, 45, 254, 178, 99, 136, 60, 242, 114, 93, 187, 48, 51, 232, 250, 80, 194, 90, 55, 112, 23, 215, 229, 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