Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c27b6566b2c591bd42c7554e0ac75e23916ca375f80380347c045b895103db5e

Tx prefix hash: bca0257d0c750fad481b25c5c57478b17ea20dcf90111238c740646069f205e4
Tx public key: f860e6467e9a0ead2fac7d0b42d2794dbcfbdd7539954d2c7e3b19af4a1cb7fb
Timestamp: 1730345259 Timestamp [UCT]: 2024-10-31 03:27:39 Age [y:d:h:m:s]: 00:147:22:19:04
Block: 1143235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105564 RingCT/type: yes/0
Extra: 01f860e6467e9a0ead2fac7d0b42d2794dbcfbdd7539954d2c7e3b19af4a1cb7fb02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 856591fb678d735c1feff0b13bdf9494a1719c7bc4af614499a71389dfe17cd9 0.600000000000 1627098 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": 1143245, "vin": [ { "gen": { "height": 1143235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "856591fb678d735c1feff0b13bdf9494a1719c7bc4af614499a71389dfe17cd9" } } ], "extra": [ 1, 248, 96, 230, 70, 126, 154, 14, 173, 47, 172, 125, 11, 66, 210, 121, 77, 188, 251, 221, 117, 57, 149, 77, 44, 126, 59, 25, 175, 74, 28, 183, 251, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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