Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75a0143045b4991fd1872c0f9960735fd792324e7941cf09c9f58359b173ff34

Tx prefix hash: bd6ea1d5c43980d7748193c6d93ba335472ef06f1eafdc385f45433f6e939962
Tx public key: 4825f971d219dbbd48ca65b090f50b2c2418c59fb5105e717f06c8681c33cb3b
Timestamp: 1722095698 Timestamp [UCT]: 2024-07-27 15:54:58 Age [y:d:h:m:s]: 00:264:22:58:19
Block: 1074931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189286 RingCT/type: yes/0
Extra: 014825f971d219dbbd48ca65b090f50b2c2418c59fb5105e717f06c8681c33cb3b02110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 493b00984a8e07e845b3fef0e519108d94f8ad89e6daec3eeb1331cf7701c22a 0.600000000000 1547450 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": 1074941, "vin": [ { "gen": { "height": 1074931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "493b00984a8e07e845b3fef0e519108d94f8ad89e6daec3eeb1331cf7701c22a" } } ], "extra": [ 1, 72, 37, 249, 113, 210, 25, 219, 189, 72, 202, 101, 176, 144, 245, 11, 44, 36, 24, 197, 159, 181, 16, 94, 113, 127, 6, 200, 104, 28, 51, 203, 59, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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