Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcc55f6e7056e090a49f9be7f5381390bf2a5890b2142da8ba1b08d359dc63ce

Tx prefix hash: 54c366f2efcbd87830df3743a13f3ce69e81a6a52eed761191477cd4e137f6b6
Tx public key: c0ca738dbc9820e2d7a9e177d37f9e6cd8f3939b0396238d4190a422e5786b09
Timestamp: 1709140446 Timestamp [UCT]: 2024-02-28 17:14:06 Age [y:d:h:m:s]: 01:058:09:22:04
Block: 967536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302746 RingCT/type: yes/0
Extra: 01c0ca738dbc9820e2d7a9e177d37f9e6cd8f3939b0396238d4190a422e5786b0902110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c46fa4993e0f44075fab70145882a934e95984ee938c7cff76b9255a1add760 0.600000000000 1427319 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": 967546, "vin": [ { "gen": { "height": 967536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c46fa4993e0f44075fab70145882a934e95984ee938c7cff76b9255a1add760" } } ], "extra": [ 1, 192, 202, 115, 141, 188, 152, 32, 226, 215, 169, 225, 119, 211, 127, 158, 108, 216, 243, 147, 155, 3, 150, 35, 141, 65, 144, 164, 34, 229, 120, 107, 9, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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