Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 349c69fff9890fc966eb8884e01791929bc794da9360cf26c02ce9bedbef4f26

Tx prefix hash: 3667e3eb4473ff8eb9af573a3cc5f8dc50eee5ced3ea34b81c2c49d264573cfd
Tx public key: dc3c7ca1d0a3ad3c64441ee518de9d5ac8e040b682eb775b7e7fa81b3178aa3a
Timestamp: 1705301700 Timestamp [UCT]: 2024-01-15 06:55:00 Age [y:d:h:m:s]: 00:363:20:01:34
Block: 935680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260491 RingCT/type: yes/0
Extra: 01dc3c7ca1d0a3ad3c64441ee518de9d5ac8e040b682eb775b7e7fa81b3178aa3a0211000000110011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17129c6aac5c83c28c11a9f30bbf29bf5bbedd41058c9ce191e9741bf87d0def 0.600000000000 1393696 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": 935690, "vin": [ { "gen": { "height": 935680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17129c6aac5c83c28c11a9f30bbf29bf5bbedd41058c9ce191e9741bf87d0def" } } ], "extra": [ 1, 220, 60, 124, 161, 208, 163, 173, 60, 100, 68, 30, 229, 24, 222, 157, 90, 200, 224, 64, 182, 130, 235, 119, 91, 126, 127, 168, 27, 49, 120, 170, 58, 2, 17, 0, 0, 0, 17, 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