Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f0066ef621026324a3bcb5de4682b3f32da016497a642256977e3db714ea421

Tx prefix hash: c892e0c834b30c617db3d684fd51b2444613700aaefc518e818b709b2f4a024e
Tx public key: 0a81fb338fa51940a1e366da865c1d213a38d5259befbeb2e5d104326e1694d5
Timestamp: 1680383056 Timestamp [UCT]: 2023-04-01 21:04:16 Age [y:d:h:m:s]: 01:330:13:17:32
Block: 730014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496854 RingCT/type: yes/0
Extra: 010a81fb338fa51940a1e366da865c1d213a38d5259befbeb2e5d104326e1694d502110000000375e3f0e9000000000000000000

1 output(s) for total of 2.339703406000 dcy

stealth address amount amount idx
00: 2bd56938fd1827b86ab0fecba35b03aec9493db51720fd92562c6e5f7a616029 2.339703406000 1175607 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": 730024, "vin": [ { "gen": { "height": 730014 } } ], "vout": [ { "amount": 2339703406, "target": { "key": "2bd56938fd1827b86ab0fecba35b03aec9493db51720fd92562c6e5f7a616029" } } ], "extra": [ 1, 10, 129, 251, 51, 143, 165, 25, 64, 161, 227, 102, 218, 134, 92, 29, 33, 58, 56, 213, 37, 155, 239, 190, 178, 229, 209, 4, 50, 110, 22, 148, 213, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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