Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b63c1e545df3496140c54a5f91f356fb7df98efbf966fd4226de95be88d85f9

Tx prefix hash: bb1a81312811ecf9b62bab73b7a6cc7faab19b66fa9ce73b576acc2e9c9b276b
Tx public key: ad400f2f5bd7e5618eb08087ff24d711437ae1444cc0ae6516f393d426dabe90
Timestamp: 1699940684 Timestamp [UCT]: 2023-11-14 05:44:44 Age [y:d:h:m:s]: 01:060:20:41:19
Block: 891265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304891 RingCT/type: yes/0
Extra: 01ad400f2f5bd7e5618eb08087ff24d711437ae1444cc0ae6516f393d426dabe90021100000005faf35c9c000000000000000000

1 output(s) for total of 0.683705494000 dcy

stealth address amount amount idx
00: 690e1d7956ca73d54b8bc148ba409ac3264850c8314019eaef58506fd84bbafb 0.683705494000 1347300 of 0

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": 891275, "vin": [ { "gen": { "height": 891265 } } ], "vout": [ { "amount": 683705494, "target": { "key": "690e1d7956ca73d54b8bc148ba409ac3264850c8314019eaef58506fd84bbafb" } } ], "extra": [ 1, 173, 64, 15, 47, 91, 215, 229, 97, 142, 176, 128, 135, 255, 36, 215, 17, 67, 122, 225, 68, 76, 192, 174, 101, 22, 243, 147, 212, 38, 218, 190, 144, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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