Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fc4b5f10a7706901dee8db5679d29c7951c6bec10371725afa4ac3b0bd15725

Tx prefix hash: 4e7318a5a2d96b48e6f46ca0f9fecf9e614f9a16e42d4e553ff912494cbf7cc2
Tx public key: e02ee4d492d88838e75dfc81f936d47d35787caa11648713966d8ef5b5bbcec6
Timestamp: 1725251723 Timestamp [UCT]: 2024-09-02 04:35:23 Age [y:d:h:m:s]: 00:111:06:36:50
Block: 1101097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79617 RingCT/type: yes/0
Extra: 01e02ee4d492d88838e75dfc81f936d47d35787caa11648713966d8ef5b5bbcec6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28a5d40bb8e1a1f35beeae01a0ad252bf99b221cee2156d9b9ca776f4a611e92 0.600000000000 1577078 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": 1101107, "vin": [ { "gen": { "height": 1101097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28a5d40bb8e1a1f35beeae01a0ad252bf99b221cee2156d9b9ca776f4a611e92" } } ], "extra": [ 1, 224, 46, 228, 212, 146, 216, 136, 56, 231, 93, 252, 129, 249, 54, 212, 125, 53, 120, 124, 170, 17, 100, 135, 19, 150, 109, 142, 245, 181, 187, 206, 198, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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