Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef3a2156cb0fe2416c6fef47d82facaaf8ce2756c3624326c4695a498a515ddd

Tx prefix hash: b62d2406a7abe26036aa1179467bfb31d504347942c3eb45bdfa6ebea24fd39b
Tx public key: 76ee2023fedfe449f1b5938e329b5a187014c1dd58d77e7dbd3cf1031cc1163a
Timestamp: 1676607035 Timestamp [UCT]: 2023-02-17 04:10:35 Age [y:d:h:m:s]: 02:267:00:17:42
Block: 698695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 710146 RingCT/type: yes/0
Extra: 0176ee2023fedfe449f1b5938e329b5a187014c1dd58d77e7dbd3cf1031cc1163a021100000001faf35c9c000000000000000000

1 output(s) for total of 2.971209932000 dcy

stealth address amount amount idx
00: e869f0030c806fe4598be9b82b5a2e180a858fc7f000e9f43a7ef53d7f14a5f2 2.971209932000 1142036 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": 698705, "vin": [ { "gen": { "height": 698695 } } ], "vout": [ { "amount": 2971209932, "target": { "key": "e869f0030c806fe4598be9b82b5a2e180a858fc7f000e9f43a7ef53d7f14a5f2" } } ], "extra": [ 1, 118, 238, 32, 35, 254, 223, 228, 73, 241, 181, 147, 142, 50, 155, 90, 24, 112, 20, 193, 221, 88, 215, 126, 125, 189, 60, 241, 3, 28, 193, 22, 58, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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