Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438638f21d9aae9adc834f95a264c3a3cf4d3440055d5a4a503c61f56088cbec

Tx prefix hash: e495ea3e585c59000712d6e99f0bfd3dc9019ff5e5a139f92f5c017f56c91ca4
Tx public key: 1192db2a9211a97c264085b2819063d3a4ff9ab74337f069969c1e136580e9fa
Timestamp: 1737591541 Timestamp [UCT]: 2025-01-23 00:19:01 Age [y:d:h:m:s]: 00:145:15:54:44
Block: 1203202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103853 RingCT/type: yes/0
Extra: 011192db2a9211a97c264085b2819063d3a4ff9ab74337f069969c1e136580e9fa021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b564ee510677cbd62e0be9a1ac61254538e7e8977d40c70d0412312afe7463f0 0.600000000000 1689875 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": 1203212, "vin": [ { "gen": { "height": 1203202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b564ee510677cbd62e0be9a1ac61254538e7e8977d40c70d0412312afe7463f0" } } ], "extra": [ 1, 17, 146, 219, 42, 146, 17, 169, 124, 38, 64, 133, 178, 129, 144, 99, 211, 164, 255, 154, 183, 67, 55, 240, 105, 150, 156, 30, 19, 101, 128, 233, 250, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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