Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f816fccf8f4f6f669e81b5061f74c7991cb10cec7af829ef96f4c491143ddebe

Tx prefix hash: e6f7de8ecb77563dbc07ac4b407a0d6ea327db6077ea023858afecabc5a0b44b
Tx public key: 0776557be8d5d3f419f0744b37fd6079ca96442a395176e9b307e213cdb53f9a
Timestamp: 1674394642 Timestamp [UCT]: 2023-01-22 13:37:22 Age [y:d:h:m:s]: 02:075:23:35:36
Block: 680341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 575941 RingCT/type: yes/0
Extra: 010776557be8d5d3f419f0744b37fd6079ca96442a395176e9b307e213cdb53f9a0211000000025029cbac000000000000000000

1 output(s) for total of 3.417808977000 dcy

stealth address amount amount idx
00: c39053eb02a0c4a37d705496cf7207ab8c9d970421ee645cc26e81316d5908c1 3.417808977000 1122372 of 0

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": 680351, "vin": [ { "gen": { "height": 680341 } } ], "vout": [ { "amount": 3417808977, "target": { "key": "c39053eb02a0c4a37d705496cf7207ab8c9d970421ee645cc26e81316d5908c1" } } ], "extra": [ 1, 7, 118, 85, 123, 232, 213, 211, 244, 25, 240, 116, 75, 55, 253, 96, 121, 202, 150, 68, 42, 57, 81, 118, 233, 179, 7, 226, 19, 205, 181, 63, 154, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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