Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76306099e61788a18fd444d97811e5471f0e4a638950b5878854053096e4704b

Tx prefix hash: e1023b264a03d1a092051f1c1ef00bb8abfb55923d8f5a5a5ea54b9c54206bd5
Tx public key: cc64e6f9a6775f774dfbda79332fbe80e6f115539de4a061f1eeeccf890a9c02
Timestamp: 1674917334 Timestamp [UCT]: 2023-01-28 14:48:54 Age [y:d:h:m:s]: 01:360:06:10:17
Block: 684673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518426 RingCT/type: yes/0
Extra: 01cc64e6f9a6775f774dfbda79332fbe80e6f115539de4a061f1eeeccf890a9c020211000000025029cbac000000000000000000

1 output(s) for total of 3.306694442000 dcy

stealth address amount amount idx
00: 7005ce64cfe94d9a45a80d7f7f69fc6646ab2484d3b95c509537a823597b0125 3.306694442000 1126942 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": 684683, "vin": [ { "gen": { "height": 684673 } } ], "vout": [ { "amount": 3306694442, "target": { "key": "7005ce64cfe94d9a45a80d7f7f69fc6646ab2484d3b95c509537a823597b0125" } } ], "extra": [ 1, 204, 100, 230, 249, 166, 119, 95, 119, 77, 251, 218, 121, 51, 47, 190, 128, 230, 241, 21, 83, 157, 228, 160, 97, 241, 238, 236, 207, 137, 10, 156, 2, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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