Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e81ffef796c426a9e131cdff055d4045829475f9c7af9e49f032e512ae39677f

Tx prefix hash: d0da67ac70be373c39aac59b743e0824d23bcd251d4d6beb3b60769b08ab8bc1
Tx public key: 932f310c5d7867f5889f22a9ecf6b348d0142d0c11d7d070a6436816ba84be3d
Timestamp: 1713550337 Timestamp [UCT]: 2024-04-19 18:12:17 Age [y:d:h:m:s]: 00:355:03:39:09
Block: 1004069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253907 RingCT/type: yes/0
Extra: 01932f310c5d7867f5889f22a9ecf6b348d0142d0c11d7d070a6436816ba84be3d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74936db67d236a83a3da3aaee39155d1dbbf61500902d988a7aec1a87f41171e 0.600000000000 1464635 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": 1004079, "vin": [ { "gen": { "height": 1004069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74936db67d236a83a3da3aaee39155d1dbbf61500902d988a7aec1a87f41171e" } } ], "extra": [ 1, 147, 47, 49, 12, 93, 120, 103, 245, 136, 159, 34, 169, 236, 246, 179, 72, 208, 20, 45, 12, 17, 215, 208, 112, 166, 67, 104, 22, 186, 132, 190, 61, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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