Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4511b1e650d402f5306a0b6785c4e8a7ca086fbb2a02e0c1a47ab4206cec76d

Tx prefix hash: a37b29fe873103f9ac3758b549ed3e9cb6432f34bdcb60859d39126229a1cd4d
Tx public key: 0e3c5a000b0bf0d868d80ac58164b474771ee9d5becd28cf873cb2a58afba769
Timestamp: 1704782946 Timestamp [UCT]: 2024-01-09 06:49:06 Age [y:d:h:m:s]: 01:124:22:41:16
Block: 931371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350440 RingCT/type: yes/0
Extra: 010e3c5a000b0bf0d868d80ac58164b474771ee9d5becd28cf873cb2a58afba7690211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 851bdeecf8e9c654d3e0f1bec14763e27777f8794ea9f110cdd039e0abb649f6 0.600000000000 1389269 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": 931381, "vin": [ { "gen": { "height": 931371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851bdeecf8e9c654d3e0f1bec14763e27777f8794ea9f110cdd039e0abb649f6" } } ], "extra": [ 1, 14, 60, 90, 0, 11, 11, 240, 216, 104, 216, 10, 197, 129, 100, 180, 116, 119, 30, 233, 213, 190, 205, 40, 207, 135, 60, 178, 165, 138, 251, 167, 105, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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