Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26149207111b709082e880f0584b85f91808da13f6a80f5ed3de5cdeaa312822

Tx prefix hash: aeda11f04de97a0537747459a2f121484760ffa83ff60eaaf5ee4e96c7cc4e06
Tx public key: 1bf2a3575d0ed825f2f58e422aab659d4a2a18aa811bd39bb65f570f2a0c5b88
Timestamp: 1720230624 Timestamp [UCT]: 2024-07-06 01:50:24 Age [y:d:h:m:s]: 00:285:06:04:50
Block: 1059464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203817 RingCT/type: yes/0
Extra: 011bf2a3575d0ed825f2f58e422aab659d4a2a18aa811bd39bb65f570f2a0c5b880211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 626a7c27b19b12dcd78f2838d8d697dc1cc6365e2803812321b3b537b4dd66f1 0.600000000000 1529933 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": 1059474, "vin": [ { "gen": { "height": 1059464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "626a7c27b19b12dcd78f2838d8d697dc1cc6365e2803812321b3b537b4dd66f1" } } ], "extra": [ 1, 27, 242, 163, 87, 93, 14, 216, 37, 242, 245, 142, 66, 42, 171, 101, 157, 74, 42, 24, 170, 129, 27, 211, 155, 182, 95, 87, 15, 42, 12, 91, 136, 2, 17, 0, 0, 0, 7, 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