Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 596611d4457912c138184b68a556e58b040cb3c029dcf7b8c2ebc867c1fb264f

Tx prefix hash: 24870d48e802ef404eec0ae526331279092ab063813b355ebb1650c42d62c307
Tx public key: e07059d4b8b6651eb39be21616db7427b206330cb6aa01c7afb07fae025617e5
Timestamp: 1706910407 Timestamp [UCT]: 2024-02-02 21:46:47 Age [y:d:h:m:s]: 01:133:10:30:08
Block: 949020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356394 RingCT/type: yes/0
Extra: 01e07059d4b8b6651eb39be21616db7427b206330cb6aa01c7afb07fae025617e50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e558c33f8c2a3e32f87fad040baef4d4b7645a1cec0e8497a873e0758634f2e8 0.600000000000 1407542 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": 949030, "vin": [ { "gen": { "height": 949020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e558c33f8c2a3e32f87fad040baef4d4b7645a1cec0e8497a873e0758634f2e8" } } ], "extra": [ 1, 224, 112, 89, 212, 184, 182, 101, 30, 179, 155, 226, 22, 22, 219, 116, 39, 178, 6, 51, 12, 182, 170, 1, 199, 175, 176, 127, 174, 2, 86, 23, 229, 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