Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03333bf5f2b8899e5a633fee248c514fb7da1a8cb33ece4578bf9827bff656a5

Tx prefix hash: b3020866dd783af4309df1c0d8d9aeae4e172876ee010a8751561c779f5246aa
Tx public key: 193a7b57ef9326bc1797fc50a9b1c58f3fae6bafc4dab22dc9a52a597973bb81
Timestamp: 1708735507 Timestamp [UCT]: 2024-02-24 00:45:07 Age [y:d:h:m:s]: 01:044:12:45:58
Block: 964172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292835 RingCT/type: yes/0
Extra: 01193a7b57ef9326bc1797fc50a9b1c58f3fae6bafc4dab22dc9a52a597973bb810211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d9fabfd974c390219de50a6b1e4e325cf9ca85b95f7a4840fd6c3d4acdfc812 0.600000000000 1423899 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": 964182, "vin": [ { "gen": { "height": 964172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d9fabfd974c390219de50a6b1e4e325cf9ca85b95f7a4840fd6c3d4acdfc812" } } ], "extra": [ 1, 25, 58, 123, 87, 239, 147, 38, 188, 23, 151, 252, 80, 169, 177, 197, 143, 63, 174, 107, 175, 196, 218, 178, 45, 201, 165, 42, 89, 121, 115, 187, 129, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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