Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bd7ee2a94f2e885c26d3dc7d4d54f7e16392f6809515c5e5711f901bde2c9d3

Tx prefix hash: 4ca589513b7acf42208ddd8aefc943488acf536249640e8c2dea579612b72b3b
Tx public key: 8d27e44dac14d354b46b23c1cac95582b0956de1528aa032de3623fc11734e7a
Timestamp: 1707031978 Timestamp [UCT]: 2024-02-04 07:32:58 Age [y:d:h:m:s]: 00:346:08:24:38
Block: 950030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247947 RingCT/type: yes/0
Extra: 018d27e44dac14d354b46b23c1cac95582b0956de1528aa032de3623fc11734e7a02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f460371c81bd2da40306db3094d218fc4020f38e292bdb08b101d4a39e6025 0.600000000000 1408578 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": 950040, "vin": [ { "gen": { "height": 950030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f460371c81bd2da40306db3094d218fc4020f38e292bdb08b101d4a39e6025" } } ], "extra": [ 1, 141, 39, 228, 77, 172, 20, 211, 84, 180, 107, 35, 193, 202, 201, 85, 130, 176, 149, 109, 225, 82, 138, 160, 50, 222, 54, 35, 252, 17, 115, 78, 122, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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