Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fb3e1b81db70a235b0c5851bd34e9b43a28794a0a5b05937e77cdb0465625fa

Tx prefix hash: 47879a9eb85e7e7601151f4c43a7c7789b79809f127d38eb6e91bce4e6a3b71f
Tx public key: 82c9dbf2d28da563b87919f4dc8f2d1bf54916c15722edc41267c151ae6c3839
Timestamp: 1708298463 Timestamp [UCT]: 2024-02-18 23:21:03 Age [y:d:h:m:s]: 01:096:00:54:05
Block: 960550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329700 RingCT/type: yes/0
Extra: 0182c9dbf2d28da563b87919f4dc8f2d1bf54916c15722edc41267c151ae6c38390211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d023066931c58b5e5627b9d7b4e437625d95a0ea1bd6d89fd5a80fc6d4197f9 0.600000000000 1420121 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": 960560, "vin": [ { "gen": { "height": 960550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d023066931c58b5e5627b9d7b4e437625d95a0ea1bd6d89fd5a80fc6d4197f9" } } ], "extra": [ 1, 130, 201, 219, 242, 210, 141, 165, 99, 184, 121, 25, 244, 220, 143, 45, 27, 245, 73, 22, 193, 87, 34, 237, 196, 18, 103, 193, 81, 174, 108, 56, 57, 2, 17, 0, 0, 0, 1, 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