Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 294401e7c02770b7e5833edf741832a173790483b1e412762d785f2fd89aa184

Tx prefix hash: 5d4c5f104f7c9a5338f4dcaaff21e7df518316366fcae0e63b9d7ffed67cdd64
Tx public key: 9c6e03d39c5ac34c9ba1f7bddea42261c5c83ef8eb3ebd63e902eaa777adc8c5
Timestamp: 1702617962 Timestamp [UCT]: 2023-12-15 05:26:02 Age [y:d:h:m:s]: 01:118:21:23:05
Block: 913439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346122 RingCT/type: yes/0
Extra: 019c6e03d39c5ac34c9ba1f7bddea42261c5c83ef8eb3ebd63e902eaa777adc8c5021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 398c8bd35b872fc52df48d422e93aef45a832c8ad429af1f73139eb379de349b 0.600000000000 1370707 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": 913449, "vin": [ { "gen": { "height": 913439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "398c8bd35b872fc52df48d422e93aef45a832c8ad429af1f73139eb379de349b" } } ], "extra": [ 1, 156, 110, 3, 211, 156, 90, 195, 76, 155, 161, 247, 189, 222, 164, 34, 97, 197, 200, 62, 248, 235, 62, 189, 99, 233, 2, 234, 167, 119, 173, 200, 197, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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