Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43242d2c74ea9a13f4012a45d642cf89dc677e247af6424b5a1ec33caa7e9408

Tx prefix hash: ff4ac7ae8ea3a19c2292c91e350a2810a973ed35a4f9c860ab85d665a144b199
Tx public key: c0140c4a2a40cb604a5208085ba419c57a6913f4dc88e2506502ee1e98b00456
Timestamp: 1728673280 Timestamp [UCT]: 2024-10-11 19:01:20 Age [y:d:h:m:s]: 00:202:19:30:52
Block: 1129465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144749 RingCT/type: yes/0
Extra: 01c0140c4a2a40cb604a5208085ba419c57a6913f4dc88e2506502ee1e98b00456021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b63ee9c8ef16ec1d97c1c2537490fcd709d225d1f673780d152d5a0fba9d4be8 0.600000000000 1612292 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": 1129475, "vin": [ { "gen": { "height": 1129465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b63ee9c8ef16ec1d97c1c2537490fcd709d225d1f673780d152d5a0fba9d4be8" } } ], "extra": [ 1, 192, 20, 12, 74, 42, 64, 203, 96, 74, 82, 8, 8, 91, 164, 25, 197, 122, 105, 19, 244, 220, 136, 226, 80, 101, 2, 238, 30, 152, 176, 4, 86, 2, 17, 0, 0, 0, 1, 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