Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50fb14cfc0724ab1e66991599f8ed484194ed814211d770b1b0750d1d6a783d

Tx prefix hash: a005642cbcaf1fe8c72e9c131587b94f922f0c8d962966c1b89a1a04d975a1fb
Tx public key: b410f83158d53824d3bd333e534ecc8774aaeba29c86d512fae80890193a1fd2
Timestamp: 1714223184 Timestamp [UCT]: 2024-04-27 13:06:24 Age [y:d:h:m:s]: 00:348:04:06:21
Block: 1009658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248893 RingCT/type: yes/0
Extra: 01b410f83158d53824d3bd333e534ecc8774aaeba29c86d512fae80890193a1fd20211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a73a32f9235738a8703272e6ff9ce1653456a049c2466a3de2f5501ea5952d4 0.600000000000 1471394 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": 1009668, "vin": [ { "gen": { "height": 1009658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a73a32f9235738a8703272e6ff9ce1653456a049c2466a3de2f5501ea5952d4" } } ], "extra": [ 1, 180, 16, 248, 49, 88, 213, 56, 36, 211, 189, 51, 62, 83, 78, 204, 135, 116, 170, 235, 162, 156, 134, 213, 18, 250, 232, 8, 144, 25, 58, 31, 210, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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